Systems and methods of processing fulfillment of transactions involving celebrities and networked users

ABSTRACT

Systems and methods are disclosed for processing transactions and associated data. In one exemplary implementation, there is provided a method for processing information associated with transactions involving a product, wherein the product may comprise an experience, a physical product, and/or a digital product. Moreover, illustrative methods may include performing processing associated with a plurality of subroutines, such as a first subroutine for handling an experience, a second subroutine for handling a physical product and/or a digital product, and/or one or more additional subroutines associated with fulfillment.

CROSS REFERENCE TO RELATED APPLICATION(S) INFORMATION

This application is a divisional of Ser. No. 13/868,031 filed on Apr.22, 2013, and claims benefit/priority of provisional patent applicationNos. 61/675,790, 61/675,795, and 61/675,801, all filed Jul. 25, 2012,all of which are incorporated herein by reference in entirety.

APPENDIX MATERIALS

Appendices, labeled “Appendix A” and “Appendix B”, are attached heretoand incorporated by reference herein in their entirety.

BACKGROUND

1. Field

Implementations herein relate to systems and methods of processinginformation associated with networked systems including features andfunctionality related to allowing first users, such as celebrities, tointeract and process transactions with other users, such as fans of thecelebrities.

2. Description of Related Information and Demand

Celebrities want to offer their work and/or content directly to theirfans without gatekeepers like networks, publishers, and record labels,and other middlemen standing in the way preventing them from doing so ortaking a large cut of their revenue they could realize from suchofferings. The few mundane options that exist have so many drawbacksthat they are typically not worth the time needed to employ them.

Fans that are passionate i.e. ‘power fan’ users are willing to pay forexclusive content and opportunities from the celebrities they idolize.Moreover, celebrities would like an easy and reputation-preserving wayto make money by selling content and experiences to fans, but there arecurrently many barriers to doing this in a meaningful and efficient way.The lack of a platform/marketplace to facilitate such transactionsresults in a great deal of pent-up supply and unfulfilled demand. Thereis a need for systems and methods that solve such problems, e.g., viaimplementations that involve features such as publicizing thisopportunity, registering and enrolling fans and users, collectingrevenue, offering access to digital content and other opportunitiesdirectly to the fans/users for a set price, for instance a monthlysubscription price, and/or delivering the content and opportunities onbehalf of the celebrity.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various implementations described inthis application, reference should be made to the Detailed Descriptionbelow, in conjunction with the following drawings in which likereference numerals refer to corresponding parts throughout the figures.

FIG. 1 is a block diagram depicting an illustrative system andinteractions between components thereof, consistent with one or moreaspects related to the innovations herein.

FIG. 2 is a flow diagram depicting an illustrative process offulfillment architecture consistent with one or more aspects related tothe innovations herein.

FIG. 3 is an illustration of an example administrative graphical userinterface consistent with one or more aspects related to the innovationsherein.

FIG. 4 is a block diagram depicting interactions among the elements ofthe systems consistent with one or more aspects related to theinnovations herein.

FIG. 5 is another block diagram depicting further interactions among theelements of the systems consistent with one or more aspects related tothe innovations herein.

FIG. 6 is an example chart showing process flow of some of the systemelements consistent with one or more aspects related to the innovationsherein.

FIG. 7 is a flow chart depicting an example of order placementconsistent with one or more aspects related to the innovations herein.

FIG. 8 is a flow chart depicting an example customer background checkprocess consistent with one or more aspects related to the innovationsherein.

FIG. 9A is a screenshot of a Celebrations experience GUI (Luminary Lane)consistent with one or more aspects related to the innovations herein.

FIGS. 9B and 9C are illustrations of exemplary experience pages,consistent with one or more aspects related to the innovations herein.

FIGS. 10A and 10B are illustrations of exemplary shopping cart/orderingpages, consistent with one or more aspects related to the innovationsherein.

FIGS. 11A and 11B are illustrations of exemplary checkout/shippingpages, consistent with one or more aspects related to the innovationsherein.

FIGS. 12A and 12B are illustrations of exemplary billing/purchasingpages, consistent with one or more aspects related to the innovationsherein.

FIGS. 13A and 13B are illustrations of further exemplarybilling/purchasing pages, consistent with one or more aspects related tothe innovations herein.

FIGS. 14A and 14B are illustrations of exemplary purchase finalizationpages, consistent with one or more aspects related to the innovationsherein.

FIGS. 15A and 15B are illustrations of exemplary confirmation pages,consistent with one or more aspects related to the innovations herein.

DETAILED DESCRIPTION OF ILLUSTRATIVE IMPLEMENTATIONS

Reference will now be made in detail to exemplary implementations,examples of which are illustrated in the accompanying drawings. In thefollowing detailed description, numerous specific details are set forthin order to provide a sufficient understanding of the subject matterpresented herein. But it will be apparent to one of ordinary skill inthe art that the subject matter may be practiced without these specificdetails. Moreover, particular aspects described herein are provided byway of example and should not be used to limit the scope of theinvention to these particular implementations. In other instances,certain well-known data structures, timing protocols, softwareoperations, procedures, and components have not been described in detailso as not to unnecessarily obscure aspects of the embodiments of theinvention.

Celebrities want to offer their work and/or content directly to theirfans/users without gatekeepers such as third party networks, publishers,and record labels, and other middlemen standing in the way preventingthem from doing so or taking revenue they could realize from suchofferings. Accordingly, the present systems and methods allowcelebrities, via platform tools and computer network features andfunctionality as set forth herein, to offer access to digital contentand other opportunities directly to the fans/users for a set price, forinstance, a monthly subscription price.

Implementations herein provide a technology platform and/or systems ormethods that may make the process for exclusive subscription baseddigital media content between a celebrity and a fan centralized withoutmiddlemen, according to some embodiments. This system provides a socialmiddleware and a data platform by reducing transactional friction andproviding transaction sharing, security, and privacy. It can alsoprovide personal verification for fans/users.

From a fan/user's perspective, there is currently a barrier between themand the person whom they admire. The fan/user often desires directinteraction with these celebrities but security concerns can keepcelebrities away from personal interactions and events that make thatviable. Currently, fans/users must work hard to find memorabiliaauctions or follow those they admire social media sites, but thefan/user must proactively search these out. Fans/users also useentertainment news, fan magazines and fan clubs, but, among otherthings, these channels of information are not personal, two-way, orunique. Fans/users may also attend live events to meet or experiencebeing near celebrities, for example, book signings, concerts,conventions, sporting events and charity fundraisers are among the mostpopular ways fans/users have an experience with their favoritecelebrities. However, all of these lack an element of uniqueness andexclusivity, which this system can facilitate.

FIG. 1 is a block diagram depicting an illustrative system andinteractions between components thereof, consistent with one or moreaspects related to the innovations herein. Referring to FIG. 1, suchsystem may serve as a direct channel that automates the connectionbetween celebrities, their fans/users and/or other people or entitieswho want to offer them opportunities. In some implementations, it may beconfigured as a connection platform providing delivery andauthentication of premium content and unique experiences for fans/users.As mentioned above, celebrity time and attention is a commodity that isoften under-leveraged. Systems herein serve as a marketplace for thatcommodity. The site and platform need not necessarily eliminateintermediary parties (agent, manager, publicist, etc.), but they mayrender their job more efficient by enabling middlemen to stick tocelebrity placements that they consider more worthwhile. A celebrity mayemploy agents in addition to the systems and methods herein to maximizeopportunities. Celebrities may also feel more comfortable using thissystem, as opposed to existing social media platforms, because it hascloaking tools that preserve their privacy while ensuring authenticityfor a fan.

Computer networks as well as associated computer components andprocessing may be leveraged to provide such communication ability anddirect exposure. The illustrative diagram of FIG. 1 shows an example ofsuch a network. For instance, the service/experience fulfillmentdatabase 110 in communication with the overall system 112. The database110 may be configured in communication with the front end web sites 120and the vendor fulfillment administration components 130. The system 112and database 120 may interact with both the front end web sites 120 andthe vendor fulfillment admin 130 components.

The front end web sites 120 are the forward facing interfaces for thecustomers and/or fans 122. The vendor fulfillment administration is therear facing part of the system that connects with the celebrities and/orvendors 132. Thus, the system 112 and database 120 allow the customersand/or fans 122 and the celebrity vendors 132 to connect, at 140, bothin an information processing context and directly. The system enablesphysical or digital experiences or services to be scheduled, planned,occur, etc., without third party complications or intervention.

In some implementations, vendors 132 may upload experience basedproducts which appear on the front end web sites 120. The customersand/or fans 122 may then find the experiences and/or products on thefront end websites 120 and purchase these experiences and/or products.The system 112 may also generate information such as confirmationmessages to both the customers 122 and vendors 132. The system 112handles the financial aspects of the transactions and/or bankinteractions. Vendor 132 and customer 122 may optionally negotiate aschedule for the experience as well as a location for the experience, beit either digital or physical. Customers 122 and vendors 132 can checkthe status of the experience deal by logging into the system 112 or byreceiving status updates from the system 112.

According to the features shown in FIG. 1 and described elsewhereherein, the present systems and methods may be configured with variousinputs and outputs. For example, implementations may process informationreceived from components associated with entities such as customers,fans, users, studios, companies, potential partners, talent/celebritiesor their representatives. Other inputs and information processedtherefrom may include data from payment related components, dataregarding items for sale or auction, content coming in for submission,information associated with cloaking and/or security, and/orcommunications from anyone who wants access to the celebrity (e.g.,brands, producer, charity, fans/users, etc).

After processing and/or transformation via the systems and methodsherein, outputs as well as information or data regarding products andexperiences coming out of the system may include experiences in bothphysical and digital form, one or more interfaces for celebrities whichallow them to approve or decline transactions, personalized orcustomized content for fans/users, streaming services, and portals orcomponents for the creation of in-house content, among other things.

With respect to systems and methods herein configured as platform-typearrangements, implementations may include or involve a socialmiddleware, other data platform and/or related components. Here, forexample, such implementations may be configurable as a social middlewarethat combines social media and online commerce. For example, a systemmay be configured as a stand-alone platform that integrates with othersocial media platforms, including features of focus and personalizationkeyed to the specific interests of a user set forth in the social mediaplatform. Implementations may also be configured as a digital repositoryof opportunities for artists, athletes, and/or other notable figures,including features that assist these individuals in more fully utilizingtheir time and earning potential.

Further, connection between celebrities and the public may be configuredwith a cloaking service/technology that provides a measure of securityand privacy for the celebrities. Such cloaking components may allowcelebrities using the system to interact with fans/users via socialplatforms without having to reveal or compromise personal accounts orinformation. Systems herein may also serve as a trusted marketplaceplatform that lies between the celebrity and the fans/users.

The present system may also include a data platform that allows forinformation, online communication, and the exchange of opportunitiesbetween those using the platform, whether they be consumers,celebrities, charities, etc. Those opportunities may be syndicatedand/or archived on their behalf, creating an idea bank that isaccessible to multiple users.

As such, implementations are provided where platforms or marketplacesthat resolve unfulfilled demand are accomplished and/or wherecelebrities achieve a reputation-preserving way to make money by sellingcontent and experiences to fans/users. According to some embodiments,for example, systems and methods herein may resolve the underlyingdrawbacks via features of publicizing this opportunity over computernetworks, registering and enrolling fans/users, collecting payments,and/or processing or delivering the content, opportunities andexperiences on behalf of the celebrity.

Without the present systems and functionality, fans or users wouldtypically receive filtered content not from the celebrity themselves butfrom the people or entities that represent them. The content that issent out directly from a celebrity via their own social media accountsis usually sent to many sources at once and may lack an exclusivity thatmany fans crave. Also, agents and middlemen generally require a fee oftheir celebrity clients, whereas the present systems may fill gap in acelebrity's opportunity lineup without such middleman influences.

There are multiple illustrative scenarios wherein the platform may beused. Some of these include the promotion of events, charitablefundraisers, memorabilia sales, agents wanting to streamline thesubmission of opportunities to the celebrities they represent, andsituations where celebrities wish to have direct control overopportunities without the need for a middleman, among other things.

Artists, athletes, and luminaries are accomplished people with time andattention that isn't fully utilized. Frame is an intangible asset, butframe has a marketplace value when attached to the time, activities, andmemorabilia of a notable person. The systems and methods describedherein provide a central way to monetize a celebrity brand and aplatform for trading on their famous names for commerce other than viaHollywood-style agents and gatekeepers or other middlemen. The systemsand methods described herein are also configured to provide alternativeopportunities to celebrities than those that may be found by an agent ormiddlemen, who may be unable or unwilling to find every opportunitygiven their own workloads and commitments.

Furthermore, the systems and methods described herein can enablecelebrities to sidestep the issue wherein an agent usually earns apercentage of a client's paycheck, even when the client finds andnegotiates his or her own deals. Not every deal needs an agent and,sometimes, a fan might be a better source for certain types ofopportunities. For example, a corporate CEO who is obsessed withbaseball might want to invite star baseball players to appear at anevent, but an agent might dismiss the request as not being worth thetime. Yet, the retired player would have liked to take part in theopportunity.

Thus, this system can help celebrities or their representatives maximizesmaller and/or alternate opportunities for local celebrities, such aslocal sports stars or regional TV personalities, this may be asignificant method by which they can extend their income and connectwith fans/users.

FIG. 2 is a flow chart depicting an illustrative process of fulfillmentarchitecture consistent with one or more aspects related to theinnovations herein. Through this system, fans/users gain access toexclusive content, experiences, and items directly through a celebrity'spage, and this system provides a platform for fans/users to complete thetransaction. This can include everything from finding what they want topurchase, arranging for shipping and billing, and finally paying tocomplete the transaction all in one centralized place.

Celebrities are looking for new, unimpeded ways to engage their fanbase. Existing social media platforms, such as those on the Internet,are useful for broadcasting comments and promoting appearances, but arenot conducive to interacting with fans/users in a potentially lucrativeway.

Some traditional methods of engaging the fan base and press are also notpopular with celebrities. For example, many celebrities dislike thepress and find promotional tours exhausting. Currently, these mediatours are the best and only way for celebrities to promote themselves asa brand. There are also not easy nor accessible ways to promote as wellas actively sell that brand when a celebrity doesn't have an upcomingfilm or TV show that's worthy of a sponsored junket.

Another problem with fan engagement is that it involves one way fansolicitation of the celebrity. For example, fans/users may have to lineup outside of theaters, send tweets, post social media messages, writefan mail and many other activities in the hope that the celebrity willpick them for an autograph, special connection on social media etc. Assuch, there is a need for systems and methods that offer morepredictable options for fans/users willing to pay to ensure that theyget the attention they crave. Implementations herein provide tools tosupplement and enhance the fan interaction with celebrities with agreater degree of certainty.

Also, current methods of reaching fans/users are limiting forcelebrities. Many don't know that they can provide a meaningfulconnection to fans/users via social media with minimal effort. Examplesof under-utilized tools are video chat, email exchange, micro-bloggingsites, etc. However, in the present implementations, especially whencombined with cloaking devices, the privacy of celebrities can beprotected while their direct interaction with fans/users increases.

There are many other problems with current celebrity marketing. Forexample, for celebrities who aren't as popular, or who have a nichelevel of frame, there are also very few good ways to make money off ofthat frame. For instance, there may a retired sports star might own somemarket-worthy memorabilia but that star may have had a relatively shortathletic career, and may not even have an agent. This can make it hardto find and tap into their existing fan base. Currently, if the athletewants to make money selling their memorabilia, he or she mightparticipate in a convention attended by fans/users. However, thatathlete may have more fans/users dispersed throughout the United Statesor the world, who aren'table to attend such a convention.

Implementations herein utilize online solutions that enable thecelebrity to sell memorabilia online, and reach a wider audience thanoffline. But selling personal memorabilia on a website may not beoptimal, and does not necessarily enhance their personal brand or image.And because celebrities sometimes only sell to niche markets, andbecause they may not have the tools to reach a large number of peoplewithin that market, it's likely that they are not receiving market pricefor their time and/or memorabilia. Systems and methods herein mayincrease and help to set the income they receive from selling thismemorabilia or making personal appearances by streamlining the salesprocess for celebrities, aiding in booking appearances and maintainingcelebrity reputations.

The illustrative flowchart 200 regarding fulfillment architecture ofFIG. 2 shows an example of how items can get fulfilled by the back endsystems. The process of fulfillment may vary as a function of the typeof product and the identity of the entity fulfilling the request. FIG. 2also illustrates exemplary order status IDs that correspond to each stepin the process. Also shown are credit charging steps. In the process,revenue is recognized when the item reaches the shipped step.

For example, each process begins with a checkout in 202. The checkouteither fails, and is cancelled in 204, or succeeds and begins thefulfillment process. If the checkout succeeds, the order is placed andchecked for fraud in 206. If the fraud check passes, the checkoutproceeds to fulfillment ready stage in 208. If the fulfillment readyfails, the order is cancelled in 204. If the fulfillment is deemedready, the order proceeds depending on whether the order was for anexperience or another product.

If the order is for an experience, the process proceeds to charge theuser in 210, for example by charging their credit card. Next, theprescheduled events proceed to pending events, whereas thenon-prescheduled events proceed to a pending schedule and schedulenegotiation until they are successfully schedules. After the pendingevent stage, the system waits for scheduled time/travel if necessary,and then the event happens. When the event has taken place, revenue maybe recognized in 260.

If the order is not for an experience, a determination may be made as towhether the vendor is to fulfill the order or not in 212. If the vendoris to fulfill the order, the next determination is whether the order isfor a physical or digital goods.

If the order is for physical goods, the goods are picked andpersonalized in 220. If there is an issue in personalization (e.g., anorder cannot be personalized as specified), the order goes back to thepicked step until the order is correct and ready to proceed. A qualityassurance (QA) evaluation is performed, and after QA approval, thephysical goods are packed. Then the order price is charged and thecarrier ships the goods. Finally, the shipped goods trigger the systemto recognize the revenue in 260.

If the goods are digital, the digital goods are produced in 230, andthen a QA check may be performed on them. If there is an issue, thedigital goods are produced again and QA checks again until the order iscorrect. Once QA approval is obtained, a charge can be issued forpayment. A produced pending stage may follow until a period to wait forscheduled delivery time elapses. After this time, the order is sent orposted. Finally, the shipped goods trigger the system to recognize therevenue in 260.

If the goods to be shipped are not vendor fulfilled in 212, and thegoods are physical, the goods are picked in 240. A QA evaluation mayalso be performed, and if there is an issue, the goods are picked againuntil QA approves. After QA approval, the physical goods are packed.Then the order price is charged and the carrier ships the goods.Finally, the shipped goods trigger the system to recognize the revenuein 260.

If the goods to be shipped are not vendor fulfilled in 212, and thegoods are digital, then the digital goods are produced in 250 andchecked by QA. If there is an issue, the digital goods are producedagain until QA approves. Next, if the QA approves, the charges areapplied. The produced goods are then pending and may have to wait for ascheduled time to send/post the goods. Finally, the shipped goodstrigger the system to recognize the revenue in 260.

As such, systems and methods herein provide transactions andmonetization for celebrities by providing payment and collectionservices. The fulfillment platform, with certain illustrativefunctionality shown in FIG. 2, allows for order fulfillment for avariety of scenarios including, but not limited to, single orders orlarge group purchases such as a group of friends joining together topurchase a private concert. For a celebrity using this system, moneypaid for their services can be available immediately via a dashboardinterface.

Systems and methods herein may also include different levels of accessfor fans/users, according to some implementations. Exemplary levels mayinclude a fee-based subscription, a set of privileges earned by actionstracked on the site, and various combinations of the two. Between levelsof free membership and all-access paid membership, there may beintermediate levels of membership with varying subscription rates, andcorresponding access to information and opportunities for the fan,according to some embodiments.

Other aspects of systems and methods herein may include transactionalsharing. Implementations may also allow for multiple types of contentsharing and transactions. These include, but are not limited to, theselling of memorabilia and the use of digital/online souvenirs as areceipt and keepsake for individual people such as fans/users,celebrities, donors and collectors, as well as organizations such asstudios, non-profits, companies, brands, and sports teams includingplayers and owners.

Transactions performed via the platforms herein may includepay-for-content/privileges features and implementations. Among otherthings, systems and methods involving pay-for-content/privilegesfunctionality may serve as a publishing platform, aggregation tool,and/or distribution channel enabling celebrities to offer exclusivecontent and a first-look rights on special offers to fans/users for afee. For example, fans/users may subscribe to a famous theme or endeavorchannel (e.g., chefs channel) in order to view a weekly livepoint-of-view broadcast of the activity or event of interest (e.g., chefcooking a particular dish). Other exemplary implementations may includefans or users subscribing to another channel, such as a famoussnowboarder's channel, in order to access an exclusive archive of tricktips and to have the opportunity to buy VIP passes and/ormeet-and-greets with the celebrity before they are made availablethrough other channels.

Systems and methods herein may utilize a central computer basedgraphical user interface dashboard that can inform the fan/subscriber ofupdated digital media content and prices, according to some embodiments.Certain personalized options, for example, may include use of celebrityvideo, including video shot by the celebrity, and/or augmented realitydigital content. Such content may include point-of-view footage.

In some configurations, this content is made exclusive in order to besold to fans or users via a number of different pricing mechanisms.Illustrative pricing mechanisms include, but are not limited by thefollowing examples:

Freemium: non-paying fans/users will still be able to access smallexcerpts of celebrity content, and a limited selection of lo-resolutionphotos; while for a fee based subscription, fans/users are able toaccess more premium, exclusive content including invitations to specialevents and high resolution photos.

Bundle pricing: fans/users are able to choose any number of celebritiesto receive exclusive content from for one price. For example, the fanmay like to follow action stars, such as Arnold Schwarzenegger, whosesubscription to their exclusive content runs for $19.99/month, forexample, but they may get themselves a deal by purchasing access toexclusive content for Arnold Schwarzenegger, Tom Cruise and Vin Dieseltogether for $49.99, for example. Such bundling may also be utilized,e.g., for a fan that wants exclusive access to 8 bands but wants a dealfor bundling them together rather than paying for access to each oneindividually.

Pay-per-view: a subscribed fan may have access to a certain tier ofpersonal celebrity videos from which they may choose for a price;additionally, a fan can buy a subscription for a certain celebrity'scontent, which would then enable them to see a given amount of thatcelebrity's videos, music or other content.

Premiercast: the present systems and methods may provide fans/users theopportunity to receive what is referred to herein as Premiercast, ahigh-concept broadcast feed direct from their celebrity, which they willself-select for free via their membership. One example of suchbroadcasting might include a personalized message from a celebrity,featuring his or her message recorded just yesterday from on the set,etc.

By means of such fulfillment/architecture features in conjunction withinnovative information processing herein, systems and methods hereinprovide fans/users and celebrities with improved ways to connect. Forexample, a fan/consumer can use the platform to verify celebritypresence and participation on the site. Another example may be theability to unite with other platform-based fans/users to create groupofferings for a celebrity, such as asking Jennifer Lopez to perform at alocal party. Still another example may be ensuring that requests forcharity performances are actually delivered, or ensuring that donatedmoneys are funneled to the right charity personnel. Furtherimplementations may process transactions like arranging events such as ameet and greet, having dinner with a celebrity for charity, sending a280-character message of inspiration (or other message) to a celebrity,ordering a birthday voice mail message for one's mom from a favoritecomedienne, purchasing digital souvenirs which include an authenticatedseal such as a digital coin which lets others know a user has had acertain celebrity experience, purchasing a note or a tag from acelebrity for one's social media profile or site, participating in acall or lesson with a hero and commemorating it on a social media site,receiving a personalized video greeting from a celebrity, having a musiclesson from a favorite celebrity, playing an online game with acelebrity, providing more niche or local offerings to local celebs suchas local chefs or sports stars, having celebrities work on projects thatare market-specific, generate reports and analytics for celebritiesabout certain markets, voting on a celebrity and their reputation via aratings system, and participating in a virtual town hall meeting.

Properly handling and processing information to achieve improvedreputation management functionality relates to other facets of thesystem, according to some embodiments. Given that a celebrity'sreputation is directly linked to his/her personal brand, reputationmanagement tools are another resource that agents and public relationspersonnel may find useful. One of these tools may be the platform'sratings system, where fans/users may rate others that they haveinteracted with, as linked to a variety of online services. Indeed, suchfunctionality provides a social incentive for behaving and delivering onpromised goods and services. Systems herein may also be configured topreclude celebrities from interacting with a fan who has a poor onlinereputation.

Another reputational element included in some implementations of theplatform's functionality is turning the system into a game-likeenvironment. Such systems may include game-like incentives such aspoints, medals, trophies, coins and progressive levels to reward usersfor engaging with the site and to keep fans/users returning to interactwith those they want to, on the system platform. These incentives mayalso be displayed on a profile page so fans see which other fans areinteracting with which celebrities and to garner a competitive urge tocollect more incentives.

Charitable giving may also be an aspect of the system platform,according to some embodiments. Many celebrities have charitable causeswith which they are connected. The charities and the celebrities thatsupport them are always looking for ways to increase awareness anddonations. Here, implementations may be configured to allow fans/usersto connect directly to their favorite star's charity in real time, ornear real-time. Further, a suggestion engine may be utilized to promoteoffers to specific users, depending on their chosen interests. Forexample, a fan who loves Betty White, a noted animal activist, mightreceive a message from Ms. White asking for donations to her favoriteshelter. In exchange the fan might receive a digital souvenircommemorating the gift such as a thank you email, from Betty White. Thesystem platform may handle the payment exchange, and support newprojects or charitable causes from Ms. White. Further, charitableopportunities may be directly submitted to celebrities or theirrepresentatives and digitally archived, so that celebrities can accessthis info at any given time.

In another example, present celebrity auctions typically only reach alimited number of off-line fans. However, there may be many more peoplearound the world who would bid on the item when given the opportunityconsistent with the innovations herein, such as via the present network,web and/or online functionality. Thus, currently, such items rarelyreceive full market value bids. Charities may use such opportunity withimplementations herein to become more visible regarding their auctionitems, to maximize the time and the attention of the celebritysupporter. This functionality is particularly helpful to smallercharities that do not have large brand names, but still want the supportof celebrities to endorse their brand, and raise awareness anddonations.

Another problem for charitable organizations is that they can miss outon donated celebrity items in situations where the celebrity must donate100% of the item/experience or nothing at all. Such limitation excludescelebrities and offerings where the celebrity would be willing to donatea material percentage of proceeds but still wants to make some money fortheir effort. Implementations herein are configured to providecustomized relationships of this nature, and via these implementations:(1) celebrities are provided functionality to customize theiropportunities, and (2) more charities receive more attention.

Additionally, celebrities often want to start their own foundations, butneed help with the administrative aspects of running a charity. Thissystem may host an umbrella organization that oversees and administersthe charity on behalf of a celebrity. For instance, someone might beable to donate to System.org/EvaLongoria Foundation. Here, then, thepresent implementations may be used to handle the financial transactionsof such a non-profit project.

This system may also be used as a vehicle for charities to fundraise anddrive traffic. These can be rated in an online rating systems as well.In addition, any non-profits need a consistent cash flow because theymay only have a few big fundraisers per year, thus making their cashflow uneven. Non-profits also need general funds for operations.Implementations herein may also be used as a source for funding generaladministrative and overhead costs, or similar aspects for which it isoften difficult to raise money.

Additionally, charities face challenges regarding distribution. They mayhave an email list and regular supporters, but if they have a celebrityitem to auction off on a visible site, they may be able to reach a muchwider audience in order to maximize bidding.

Systems and methods herein may also archive offers or fan-based ideasfor celebrity performances or work, including a timeline.Implementations herein may be configured to utilized these to providemore niche offerings to local and regional fans/users. Also to offermarket tools for agents and managers. Additionally, as discussed above,to enable charities to smooth out their funding year-round, and stayvisible. Implementations may offer celebrities and their teams aninterface such as a control panel enabling them to post offerings forsale, get alerts for tasks required to fulfill sales, respond to offers,and track the status of their listings. This system can add real-timescheduling, delivery and inventory to transactions for celebrities.

FIG. 3 is an illustration of an example administrative graphical userinterface consistent with one or more aspects related to the innovationsherein. Referring to FIG. 3, a map of an illustrative Graphical UserInterface (GUI) of exemplary vendor administration functionality isshown. In the illustrative GUI depicted, a ‘to-do’ button 302 maydisplay what the vendor needs to do now. The ‘to-dos’ 302/‘currentto-dos’ 304 may be the first screen that shows up when the vendor logsin. In some implementations, only items that need to be done and can bedone now show up on this screen. Items may be sorted by priority. Eachitem type has a custom UI that explains to the vendor the next steps.

The GUI 300 may include a product management button 306, ahistory/reports button 308 an account button 310, and a calendar button312. A list of notifications may also be displayed, for exampleincluding display for the scheduled events happening now section 314,the physical items that need fulfillment now 316, Tweets/Facebook posts318, the scheduled experiences that need a time section 320, the requesta quote section 322, and a messages section 324. The GUI may alsoinclude a fulfillment section 330 and a marketing section 340. Thefulfillment section 330 may include physical items, events, Facebook,and Tweets sections. The marketing section 340 may include Tweets andFacebook sections.

Some examples of the ways a celebrity may use the platform includeallowing a direct conduit to a celebrity for any individual or entity,such as a fan or a movie studio or a partner that wants to provide themwith work or a project, using virtual opportunities to connect withfans/users on social media, and/or enabling a celebrity to better managetheir appointments and career opportunities. With this system, they areable to do as much or as little offered work as they like. They are alsoable to search for types of projects which may be offered.

Additionally, celebrities may manage their own career remunerationwithout paying fees to a middleman. They are also safer in theirpersonal interactions with fans/users, due to cloaking mechanisms. Theymay offer content directly to a celebrity's fan base, thereby bypassingmiddlemen and distribution channels and effecting a grass-roots saleseffort. An example might be a band's pre-selling an album to dedicatedlisteners or fans. Celebrities may take digital control of tracking,publication, and distribution of anything to do with a celebrity's nameor brand. They may publish celebrity content such as direct certainphotos, post on update on a social media site, and share a positivemovie review. Systems and methods are configured such that celebritiesmay steer multiple sites from one control panel and streamline thepublicity process. Implementations may be configured to deliver a wishlist to fans/users or thank you notes to those with whom they haveinteracted. Celebrities may be provided functionality enabling them todonate all or some of the proceeds of a certain concert to charity, andthe giving process can be automated. Systems may also be configured toensure that charity moneys, based on appearances, are delegated to theright personnel, thereby reducing risk of scandal and misappropriation.

As celebrities sometimes have resources at their disposal, this systemcan also feature anyone including lesser known celebrities, which canflatten out the industry's payment curve by enabling many celebrities tobetter find their sales niche. It may also allow fans/users through themiddlemen gatekeepers. Systems and methods herein may initially leverageother people's content and then create their own content. They may alsobe configured to create and/or involve a pay-wall service within analready premium channel.

This system may offer curated and targeted distribution for exclusivecontent, according to some embodiments, for example via the GUI. In somecases this system may offer its own publishing tools. In other cases itmay enable celebrities to use existing publishing platforms and toolssuch as YouTube and Flickr with additional paywall features provided bythis system. For instance, the celebrity publishes a video on YouTubebut adjusts the videos setting so it is only viewable to paying membersof their channel on the present platform. Systems and methods herein maybe configured to do this by marking a celebrity video as private, andembed it behind a paywall, then automatically generate messages tofans/users, who will be enabled to pick their “social circle” of friendsor other fans/users who can pay for this content.

The scarcity of celebrity digital media content can makes it morevaluable and exclusive thus helping maximizing the potential for moremonetization opportunities. This system can provide the ability ofcertain limitations to a given celebrity's digital media content byeither offering it for a limited time, or by limiting the number ofpeople who can download or purchase it. Also as an example, asubscription to certain content can be limited to a fan/user's Facebookfriends, a select ten of whom can be invited to purchase it—such contentmight be a video, a piece of music, an invitation to a meet-up online orspecial event or other forms of exclusive content.

The present content distribution functionality may enable content to beavailable world-wide over a wide area network such as the internet. Tothis effect, this system can create niche site areas for internationalcelebrities, as well as U.S.-based ones.

Systems and methods herein may leverage existing publishing platformsand can publish exclusive content. Fans/users can self-select for freeon this system's publishing platforms, based on their personal “opt in”subscriptions. These include, but are not limited to, social networkingsites such as FACEBOOK™, TWITTER™, TUMBLR™, WORDPRESS™, YOUTUBE™,PINTEREST™, INSTAGRAM™, VIMEO™, and any other publishing platform andeach will notify a fan when their chosen celebrity publishes something.The user/celebrities can select published content as “Private,” whilethey embed or Share their content with this system's platform.

Celebrities can aggregate their exclusive content and create bundles—forexample, $19.95 for three celebrity videos, $29.95 for five. A freepreview of the content can be included on the celebrity's pages.

Systems and methods herein may also provide celebrities with socialmetrics, which will help them know and cultivate their fan bases,according to some embodiments. Implementations of this system alsoprovide celebrities with tools to develop their brand and offerexclusive access to content whether it be for free or for a premiumsubscription model. As systems herein are well-suited for power fans,celebrities may be provided with functionality to involve their fans inobtaining input from them to help determine who will go on tour withthem, or who should co-star in a movie with them, as in prizes orcontests, for example. Further, systems may give power fans first accessto celebrity live performance tickets, as away to create a continuallymeaningful connection, and an important, continuous feedback loop forcelebrities, according to some embodiments.

Many options may be utilized to connect with fans. Some of those optionsinclude social networking websites such as Facebook, for example.Systems and methods herein may be innovatively utilized with such socialnetworking sites, e.g., by using the Facebook canvas as an iFrame byhaving a DRM player inside of an API component of the system.

Third Party Integration

The system platform may be configured as a stand-alone site, and/or itcan also integrate with third party social network websites and mobileapplications. These configurations allow establishment of userpreferences, such as identifying a user's top celebrity idols or usingthe site's recommendation engine to maximize fan engagement. Therecommendation engine may also integrate information from third partiesand suggest items or donations that a fan is able to purchase or makefrom a celebrity wish list.

FIG. 4 is a block diagram depicting interactions among the elements ofthe systems consistent with one or more aspects related to theinnovations herein. FIG. 5 is a diagram showing how the system mayintegrate with other platforms, including fulfillment and paymentfeatures. As shown, the fan or user may utilize a front end user facinginterface provided by one or more third parties and/or this systemitself. The product type checkout may occur either through this systemor the third party system. The back end system may include theexperience fulfillment components and a database to store the paymentand fulfillment details.

The system connection platform may be a stand-alone website, a Facebookapp, or an interface to other third-party social media platforms. Otherimplementations may be applications such as an HTML 5 application, whichwould provide access to the platform for those who are not able todownload, and have no access to the application.

FIG. 4 provides a high level overview of some illustrative functionalityand architecture of an exemplary system. Product information may bestored in a first database 400 configured to hold product informationand control the front end. This data can be displayed in a variety ofone or more front end components which can be controlled by the firstdatabase 400. Exemplary front end components and their check out modulesmay be different websites 402, 404, 406, 408, co-brandedcomponents/websites 410, 412, 414, 416, and/or front end may include oneor more mobile apps components 418, 420. Each front end can include aproduct selection UI, through which a user may view and/or selectproducts 402, 406, 410, 414, 418. Each front end can also display UIscreens and fields to collect customer information specific to the manyproduct types offered 404, 408, 412, 416, 420. Order data along withfulfillment information can be received via the front end UI by thebackend system 422 and can be stored in a second database 424 configuredto manage order and fulfillment data.

FIG. 5 is another block diagram depicting further interactions among theelements of the systems consistent with one or more aspects related tothe innovations herein. As with FIG. 4, a first database 500 may containproduct information and may provide the product information forprocessing and use by the front end components. Product selection UIfront end components can display product information and receive productselections in 502, 506, 510, 514, 518. Users can view, select, andchoose to purchase products, and the front end can receive customerinformation related to a purchase in 504, 508, 512, 516, 520. The seconddatabase 522 and backend system can receive the customer information viathe front end and manage the order and fulfillment process, at 522. Oncean order is placed, it may be determined whether it is to be fulfilledinternally, at 524. If so, the order is handled by an internalfulfillment process powered by internal admin UI 526. If not, the orderis handled by celebrities/vendors who use the vendor admin UI, at 528,which coordinates what things the vendor needs to do to fulfill customerorders and when they should be done. As with the customer front endscreens which are customized based on the product type and other productinformation, the backend systems can process information differently asa function of the type of product being purchased. After fulfillment hasbeen processed in 528 or 528, the order is actually fulfilled in 530(i.e., an order can be shipped or an experience may take place).

System Processing and Navigation

FIG. 6 is a flow diagram showing how selection of product types andproduct type flags may drive the presentation of the user interfacescreens for ordering, selection, and payment, consistent with certainimplementations herein. These selections can also control the back endfunctionality required for product fulfillment. The architecture allowsnew product types to be created without code changes. Many producttypes, including types that are new to ecommerce/software, aresupported. Each product type has a unique set of fields and UI screensfor a user to complete. Examples of product types may include thefollowing types. A ‘Product Physical’ or ‘Normal Product’ is a normalphysical product (such as a product which may be sold via conventionale-commerce systems). A ‘Facebook Post’ is a Facebook post from acelebrity or vendor which can be purchased. A ‘Twitter Follow’ is aTwitter follow from a celebrity/vendor which can be purchased. A‘Twitter Shout Out’ is a Twitter shout out from a celebrity/vendor whichcan be purchased. A ‘Chat Video’ is an online video chat with acelebrity/vendor which can be purchased. A ‘Chat Phone Call’ is a phonechat with a celebrity/vendor which can be purchased. An ‘Event Physical’is access to an event from a celebrity/vendor that takes place at apreset place and time which can be purchased. A ‘Subscription’ issubscription access to periodic content from a celebrity/vendor whichcan be purchased. A ‘Badge’ is a customized badge from acelebrity/vendor which can be purchased. An ‘Event Preannounce List’ isa special experience from a celebrity/vendor which can be purchased andmay be selected from a list of events. For example, a meet-and-greatwith the celebrity/vendor at any one of the concerts in a musician'sconcert tour may be a product in this category. A ‘Message Video’ is acustom video message from a celebrity/vendor which can be purchased. A‘Meeting Schedulable Digital’ is a digital meeting with thecelebrity/vendor which can be purchased and which may have a time thatis negotiated between the buyer and the celebrity/vendor. A ‘MeetingSchedulable Physical is a physical meeting with the celebrity/vendorwhich can be purchased and which may have a time that is negotiatedbetween the buyer and the celebrity/vendor. A ‘Gift Certificate Digital’is a gift certificate for a digital product or experience such as thosedescribed above, and a ‘Gift Certificate Physical’ is a gift certificatefor a physical product or experience such as those described above.

A product types table 600, which has a record for each product type, maybe included in the system. Implementations herein may utilize UI elementfeatures that present different UI fields and UI screens based on theproduct type of each product. Each product type in the table 600includes product type flag data 602 which can be used to identify theproduct types within the system. Here, for example, variousimplementations and functionality may be achieved by performingprocessing as a function of data fields which represent the product typeflags 602 in the data records/fields of the product types table 600.Also, product type flag field definitions 604 may be provided to definecertain characteristics of each product type. For example, product typesmay be defined as ‘isPhysical’ or ‘isExperience’, indicating whether theproduct is a physical product or an experience, respectively. Producttypes may be defined as having a ‘PresetTime’ or ‘TimeNegotiable’,indicating whether the product (e.g., an experience) has a set time orhas a time that can be agreed upon between the buyer and thecelebrity/vendor. Product types may be defined as ‘LocationNegotiable’,indicating whether the product (e.g., an experience) has a location thatcan be agreed upon between the buyer and the celebrity/vendor. Producttypes may also be defined as ‘ContactInfoNeeded’, ‘FacebookIdNeeded’,‘TwitterHandleNeeded’, ‘RecipientNameNeeded’, and/or ‘CommentNeeded’,indicating whether certain information such as contact, Facebook,Twitter, name, or comment information is required from the buyer inorder to complete the product transaction. One example involving a SQLrealization of product types table functionality is set forth inAppendix A.

In addition, other customization functionality may be controlled byproduct flags 606 in the product types table 600 for each product. Forexample, an ‘is Personalized’ flag may indicate that the product ispersonalized to the buyer. ‘BackgroundCheckRequired’ and/or‘AgeVerificationRequired’ flags may indicate that additional informationabout the user (i.e., a background check or an age verification) isrequired to complete the product transaction. In addition, furthercustomization functionality may be driven by the order flags fields 608,which are fields specific to each individual purchase of a product. Forexample, an ‘is Gift’ flag may indicate that the product was purchasedby the buyer as a gift for another party. One example involving theflags in the product types table is set forth in Appendix B.

When a product types table 600 has been generated, including some or allof the data described above, it can be used in ordering celebrityproducts. For example, the product checkout screens described in thecontext of FIG. 5 above can present a variety of UI screens to a user.In the example of FIG. 6, an optional UI screen A with variable fieldsis presented in 610. This screen presents options for a user to select,such as the type of product to be purchased. Depending on which optionsare selected, the system can present another optional UI screen B in 612or a required UI screen X in 614. For example, screen B can presentoptional fields associated with the choice received via screen A. Oncethe fields in screen B have been entered, the system can proceed to therequired UI screen X in 614. Likewise, depending on what is received viascreen X, the system can display optional UI screen C 616 or required UIscreen Y 618. After all required fields (and/or optional fields) havebeen displayed and data has been received, the order is placed in 620.Note that this sequence is an example only, as other sequences of UIscreens consistent with the innovations herein may be displayed to auser in the process of placing an order.

FIGS. 7 and 8 are exemplary flow diagrams of illustrative orderplacement and customer information processing functionality,respectively, consistent with one or more aspects related to theinnovations herein. These diagrams provide an illustrative overview ofhow products with an experience product type may get processed by theback-end, after purchase. While back-end systems and methods may behavesimilarly to conventional ecommerce back-ends when processingconventional products, implementations herein may possess various novelfunctionality involved with efficiently handle experience product types.With regard to making an experience happen, multiple people must bebrought together in the same place at the same time. Multiple people areinvolved and difficult to schedule a time and place that works for allinvolved. Determining, coordinating and communicating all the details ofthe logistics required for an experience is too time-consuming anderror-prone without solutions such as those provided via the systems andmethods herein. Among other things, implementations herein enablefulfillment of many experience orders simultaneously, with variousinnovative processing, and without losing track of any details. Suchimplementations provide features and functionality that are essential toproviding a good experience for the buyers and sellers involved, whileaccomplishing objectives at a low cost to provide better value tocustomers while still maintaining suitable/sensible profit margins.

FIG. 7 is a flow chart depicting an example of order placementconsistent with one or more aspects related to the innovations herein.FIG. 7 provides one illustrative high level overview of a back-endfulfillment process for experiences. The illustrative backend processingof an order shown here begins when the order is successfully placed onthe front end by a customer, at 702. In some cases, a purchase is madeas gift 704, in which case purchaser is not buying the experience forthemselves, but instead is giving it as a gift to another person. Therecipient will receive a Gift Ticket in this case, at 706. If the giftcase, the customer may be charged immediately after the Gift Ticket issent, at 710, which is earlier in the fulfillment process than chargingsometimes occurs in the non-gift case.

As a next step in this illustrative fulfillment process, at 708, one ormore information gathering processes may be performed, e.g., to makesure all the necessary information has been gathered from the customeror the gift recipient, such as information to schedule the experienceand/or do a background check if necessary. Exemplary details of what mayoccur during an illustrative information gathering process 708 are setforth in connection with FIG. 8. If this processing fails, the order maybe canceled, at 714. After a successfully completed background checkand/or scheduling processes, at 712, payment may be effected, e.g., thecustomer's credit card may be charged (settled) to collect the revenuefor experiences. Here, the credit card may have been previously beenauthorized for the amount of the purchase, so unless the authorizationhad expired, the credit card charge/settle will succeed. If the originalauthorization has expired, and the credit card was not able to beauthorized again, then the order may be cancelled 714 at this point dueto the inability to collect payment. If the money was successfullycollected, an event summary email may then be sent, at 716, summarizingwhat will happen and when. If the experience is not a gift, anexperience memento ticket may be sent to the buyer, at 718.

After such optional processing is performed, final logistics such asfinal location logistics may be determined and entered into the system,at 720. In some cases, for example, the experience may happen at alocation selected by the customer or giftee. In other cases, it willhappen at the location chosen by the luminary/vendor. In either case,the final logistics information will be entered into the system, so theycan be communicated to the customer and/or the celebrity/vendor, as insteps 722-734, via various email or other communication(s) such as thefollowing.

For example, implementations herein may send out up to two additionalreminder emails, the first of which will be sent 1 week before theexperience, at 726. If there's greater than 1 week until the experience,the system may wait until there is just 1 week before the experience tosend the reminder/logistics email, at 724. Another reminder/logisticsemail may be sent closer in time, as well, such as 1 day before theexperience, 728, 730, 732, unless there isn't more than a day before theexperience. Finally, the experience that the customer purchased occurs,734, and the presently described, illustrative experience fulfillmentprocess is complete.

FIG. 8 is a flow chart depicting an example customer background checkprocess consistent with one or more aspects related to the innovationsherein. Systems and methods, here, may provide functionality that helpmonitor and maintain security for celebrities. Such celebrities mayspend a great deal of money on physical security when they make personalappearances, but they cannot attend every event in person because notevery event can be vetted. As such, these background/securityimplementations and tools provide personalized interaction withfans/users while maintaining a layer of security and privacy.

Additionally, there is a need for a fan to verify that an onlinecelebrity, or their piece of memorabilia, is authentic. Authenticationof items signed by notable people affects the value of the item, as wellas the reputation of all involved in its sale. Furthermore, there aresome challenges to the process of purchasing and consumingcelebrity-related content. Consumers have an expectation that they canpurchase content on-demand, however region-locking and release windowtechnologies often impede this process, even if consumers will buycontent legally when available, but will resort to pirating if notlegally available. There is a definite need for a trusted verificationsource, as well as a digital record of the transaction.

Other example uses for this system involve using Security APIs As aComponent of the System, such as implementations that includevideo/audio fingerprinting.

Further, systems and methods herein may involve various features relatedto security, according to some embodiments. For example, implementationsare configured to handle security problems in a multitude of ways,including watermarking, to ensure paywall integrity, and Digital RightsManagement (DRM). Such security may be useful for celebrities to protecttheir online content and identities.

Methods here may also involve verification of the various opportunities,according to some embodiments. Here, implementations may be configuredwith features to protect the reputation of the celebrity and/or theauthenticity of the good, service or offering, things that celebritiesare concerned about. Such system verification processes may ensure thatopportunities for celebrities are legitimate, and backed by whom theyassert they are backed. Functionality may also be provided to assurefans/users that the celebrity experience is authentic. Further,implementations may be configured with a ratings system for bothfans/users and celebrities, to help provide measures of assurance forpeople on the platform, according to some embodiments. Suchimplementations may even incorporate information from other social mediasites to make it more interactive.

Referring to the illustrative processing shown in FIG. 8,implementations here may first check to see if the products in thisorder require scheduling or a background check, at 802.1 f not,processing may proceed through steps 822 and 838, to the end 848, afterwhich the system continues at step 712 in FIG. 7.

If scheduling or a background check is needed and hasn't already beenaccomplished, then processing may be performed to reach out to thecustomer to collect this information, at 804. Such processing may resultin the initiation of various communications, such as emails, phonecalls, and/or other methods or functionality. Further illustrativeprocessing may be performed, at 806, if a response from the customer isnot received within a certain time period, such as 7 days. Here, if theitem ordered is a gift 808, then implementations may follow up with anemail to the giftee, at 810, as well as with an email to the buyer, at812. Such communications are optional and serve as additional prompts toget the information needed to fulfill the experience item. Turning backto the illustrated processing, implementations may wait up to a setperiod, such as 7 days, for a response, at 814. If no response isreceived, attempts to contact the customer and/or giftee may beescalated, at 816. Such escalation may include functionality in the formperforming processing to initiate phone calls or other communications bya customer service/concierge component or individual. Again,implementations may wait another set period such as 7 days, at 818, and,if a response is still not received, additional processing may beperformed. For example, implementation may wait another period of time,such as 1 year, for a non-gift order 844/842, after which the order willbe cancelled, at 840. For a gifted order, implementations may waitalmost indefinitely for a response, at 846.

If at any point in the process, a response is received from thecustomer, then the various information needed from the customer may becollected, at 820. If a background check is required, information iscollected from the customer, or from the giftee in case of a gift. Ifscheduling is required, information is collected about the customer's orgiftee's availability. Here, for example, implementations may beconfigured to collect at least 3 days and times that the customer isavailable. Once the needed information is collected from the customer,the system accesses information regarding subsequent processing to beperformed, at 822. For example, if scheduling is required 832,processing may be performed to contact the luminary/vendor to see if anyof the dates and times that the customer is available match up with theavailability of the luminary/vendor, at 834. Implementations may beconfigured such that the customer or giftee cannot just specify a timethat they want the experience to happen, because the luminary/vendormust also be available for the experience to occur. If any of the timesspecified by the customer are acceptable to the luminary/vendor, thenthe agreed upon date and time is confirmed and processed by the system,at 836. If the luminary/vendor is not available at any of the timesspecified by the customer, then implementations may perform processingto allow the luminary/vendor to enter several dates and times into thesystem as to when the luminary/vendor is available, at 836.

If, at 824, a background check is required, then the background checkprocessing/processes may be started at 826. The results of thebackground check, once complete, will get entered into the system forprocessing, at 828. The system may then evaluate ifscheduling/background check process had completed successfully, at 838.If the celebrity/vendor had not agreed with the customer availabledates, but had specified alternatives, then the scheduling problem isdeemed fixable and the system loops back to contact the customer orgiftee, this time communicating to the customer the alternative timesthat the vendor is available, as per step 802 and onward. It is possiblethat the customer and luminary/vendor cannot find a mutually agreeabletime to schedule, in which case the order is canceled, at 840. If thebackground check fails outright, the order may also be cancelled 840. Insome cases, a background check may end up in a marginal state, thatneeds further evaluation. In these cases, various processing may beperformed as to how to proceed. In these marginal cases, processingmight be performed to reach out to the customer again 838, 802, e.g. togather additional information to help decide whether to accept or cancelthe order. If all the checks pass successfully, the scheduling andbackground check processes are flagged as complete, at 848, and theprocess proceeds from step 708, in FIG. 7, to step 712.

Celebrations Example

FIGS. 9A, 9B and 9C are illustrations of exemplary experience pages,consistent with one or more aspects related to the innovations herein.Referring to FIG. 9A, an exemplary experience or Celebrations experiencewire diagram of a webpage layout is shown. Implementations here, forexample, may be integrated into social media, such as Facebook, via anapplication (app) component or module, and may have an application (app)icon that the user clicks to go to a Celebrations AppCanvas page. Theapp module can inform the fan/user on the offerings available in theCelebrations experience.

Additionally, the example webpage has many image spaces which can beloaded with images 902 to provide additional advertising of variousexperiences or offerings available. Details about each Celebrationoffering may be displayed using areas or buttons on the page. In someexamples, the user can roll over and click on an area or button to viewa pop-up window with additional information about that particularexperience. A pop-up window (not shown) may be included to allow theuser to view videos, images and text within it, describing it in moredetail and possible sub-options available. Further, the user can clickthe show price buttons 904 to see what the cost of that experience maybe. Other features on the page allow users to send messages to thecelebrity 906 and suggest your own dream 908. Also on this example pageis a logo 910 of a charity that this celebrity supports.

FIG. 9B is another exemplary page consistent with aspects of theinnovations herein. In this example, e.g. run via Facebook systemprocessing, the page allows users to click the Celebrate With Me 920button. The identification area 922 may then describe the celebrity andadvertise the Celebration. An example experience, here “let's havelunch” 924 is highlighted. The user may inquire more about thisexperience by clicking on it or hovering over it. The pop-up window 926can show more details about the experience and allow the user to “Buy itNow.” Further, the user may click the button to “Learn More” 928 inorder to learn more details yet. to In FIG. 9B, the user can click the“Buy Now” button 926 and go directly to the permissions step, then tothe Celebrations Product Page associated with that button. FIG. 9C is awire diagram of FIG. 9B in the Facebook setting.

FIG. 10A is an illustration of exemplary shopping cart/ordering pages,consistent with one or more aspects related to the innovations herein.Items 1010 added to the Shopping Cart will display in the order theywere added, and remain for X days. Some items allow users to updatequantities from here, and some only allow a single purchase (e.g.Twitter or Facebook items.) The user can select the “x” next to aproduct and it will be dynamically removed from the order summary. Ifthe user updates the quantity the page will auto-refresh and display theupdates quantity, and the updated order total automatically. Users mayselect “Check Out” button 1012 in order to complete the order. A “NeedHelp” module 1014 will display FAQs and the support email address. Thismay be static content added by the editor. A “Continue Shopping” button1016 may be included to take the user to the page previously viewed whenthe Shopping Cart was accessed. A shipping estimator 1018 will allow theuser to enter her zip code, select the shipping speed and view theshipping costs she will expect to pay based on what is currently in hercart. The shipping charge may be dynamically displayed in the module andin the Order Summary module. A Check Out button may take the user intothe Checkout Flow/Shipping page, as shown and described herein. FIG. 10B is a wire diagram of FIG. 10A.

FIGS. 11A and 11B are illustrations of exemplary checkout/shippingpages, consistent with one or more aspects related to the innovationsherein. Referring to the illustrative shipping page of FIG. 11A, a usermay enter their zip code here and the related city(s) will appear in adrop-down menu for the user to confirm city name dynamically. “UnitedStates” (or other related country or US territory) will be displayedbased on zip code entered as well. The Order Total 1012 will dynamicallyupdate to reflect in shipping charges. The shopping cart contents 1114will be viewable in this space on every page of the Shopping Cart pages.The user can click “Edit Cart” button 1116 at any time to return to thecart to update product quantities or remove or add a product. FIG. 11Bis a wire diagram of FIG. 11A.

FIGS. 12A and 12B are illustrations of exemplary billing/purchasingpages, consistent with one or more aspects related to the innovationsherein. Referring to the illustrative billing page of FIG. 12A, the usercan click the “Edit” button 1210 and return to the “Shipping” page tochange the shipping contact details. The user can update the shippingspeed at any time by selecting it in the dropdown menu. This willdynamically update the Order Total module in the in the upper leftcorner. The user can select “Pay with PayPal Account” 1212 and bedirected off the Celebrations site to the PayPal page associated withthis account. Once fulfillment has been made, the user will beautomatically directed back to this page to complete the purchase path,and PayPal will be in a selected state. The user can select “Pay byCredit Card” 1214 and the page will dynamically expose all the relevantform fields for the user to complete a credit card transaction. As shownin Fs 12A and if the user selects “Pay by Credit Card” the page wouldautomatically display relevant credit card authorization fields. FIG.12B is a wire diagram of FIG. 12A.

FIGS. 13A and 13B are illustrations of further exemplarybilling/purchasing pages, consistent with one or more aspects related tothe present innovations. In the illustrative billing page of FIG. 13A,for example, the user may enter information into all the required fieldsin order to purchase 1310. On click of the “Continue” button 1312, thecredit card will be checked for fraud or incorrect entries, and returnerrors associated with them, as shown in the drawings. The selectedpayment method may be displayed in this module as shown. The user clickon the “Edit” button in order to return to the Billing Page to changethe method. The user can create an account at the end, if an account hasnot yet been made. For users that have already created an account, allfields will be prefilled, and password/confirm password fields showing“*****” to mask the password. The “Send Me Email Updates” checkbox willbe pre-selected. The user can bypass creating an account and go directlyto the Confirm Order page. FIG. 13B is a wire diagram of FIG. 13A.

FIGS. 14A and 14B are illustrations of exemplary purchase finalizationpages, consistent with one or more aspects related to the innovationsherein. Referring to FIGS. 14A and 14B, user billing information 1410may be displayed from the previous input. The Account information area1412 allows users to sign up for an account if they have not previously,or select “No Thanks” button 1414 to merely complete the transactionwithout signing up. The “Complete Purchase” button 1416 will submit thepurchase and return a confirmation message to the user when thetransaction has been made. FIG. 14B is a wire diagram of FIG. 14A.

FIGS. 15A and 15B are illustrations of exemplary confirmation pages,consistent with one or more aspects related to the innovations herein.Here, such confirmation page confirms the order, and may provide anorder number 1510 and a link back to the Landing Page for thisCelebrations site, as shown in FIGS. 15A and 15B.

Overall, one illustrative implementation encompassing an array of theabove features may be characterized as a method of processing datacomprising: processing, with a front end module in communication with aprocessor, product data from a first database; performing processing,with the front end module, of information for display at least some ofthe product data; processing, with a checkout module in communicationwith a processor and the front end module, a checkout of the product,the product comprising an experience, a physical product, and/or adigital product; and receiving, with a backend module in communicationwith a processor and the checkout module, data associated with thecheckout of the product from the checkout module. Moreover, the methodincludes, when the product comprises an experience: determining, withthe backend module, whether the product has been purchased as a gift;when the product has been purchased as gift, sending, with the backendmodule, a gift ticket to a recipient; processing, with the backendmodule, a charge associated with the product; when the product has notbeen purchased as a gift, sending, with the backend module, a ticket tothe user; determining, with the backend module, a time and placeassociated with the product; sending, with the backend module, areminder to the user and/or the recipient at a time before the timeassociated with the product; and receiving, with the backend module, anotification that the experience has taken place; and when the productcomprises a physical product and/or a digital product: determining, withthe backend module, whether the product will be fulfilled by a vendor orby the backend module; when the product will be fulfilled by the vendor,sending, with the backend module, information associated with theproduct to the vendor and receiving, with the backend module, anotification that the product has been fulfilled; when the product willbe fulfilled by the backend module, fulfilling, with the backend module,the product; and processing, with the backend module, a chargeassociated with the product after the product has been fulfilled.Further, the product may be associated with product data comprising oneor more of a plurality of product types, one or more of a plurality ofproduct type flags which describe one or more of the plurality ofproduct types, and one or more of a plurality of product type flag fielddefinitions which define a characteristic of one or more of theplurality of product type flags.

Further Implementations and Nuances

Systems and methods herein implemented via stand-alone webpageconfiguration(s) may not be appropriate for all celebrities. In thesecases, implementations may be configured to produce a white-labelversion of the platform. For example, celebrity may have a large fanbase, but may also need assistance in order to maintain and not damagetheir brand. Conversely, systems and methods may also be configurable tocreate custom platforms and functionality for other celebrities such asa George Clooney or Angelina Jolie.

The innovations herein may be implemented via one or more components,systems, servers, appliances, other subcomponents, or distributedbetween such elements. When implemented as a system, such systems mayinclude an/or involve, inter alia, components such as software modules,general-purpose CPU, RAM, etc. found in general-purpose computers,and/or FPGAs and/or ASICs found in more specialized computing devices.In implementations where the innovations reside on a server, such aserver may include or involve components such as CPU, RAM, etc., such asthose found in general-purpose computers.

Additionally, the innovations herein may be achieved via implementationswith disparate or entirely different software, hardware and/or firmwarecomponents, beyond that set forth above. With regard to such othercomponents (e.g., software, processing components, etc.) and/orcomputer-readable media associated with or embodying the presentinventions, for example, aspects of the innovations herein may beimplemented consistent with numerous general purpose or special purposecomputing systems or configurations. Various exemplary computingsystems, environments, and/or configurations that may be suitable foruse with the innovations herein may include, but are not limited to:software or other components within or embodied on personal computers,servers or server computing devices such as routing/connectivitycomponents, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, consumer electronicdevices, network PCs, other existing computer platforms, distributedcomputing environments that include one or more of the above systems ordevices, etc.

In some instances, aspects of the innovations herein may be achieved viaor performed by logic and/or logic instructions including programmodules, executed in association with such components or circuitry, forexample. In general, program modules may include routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular instructions herein. The inventions may also bepracticed in the context of distributed software, computer, or circuitsettings where circuitry is connected via communication buses, circuitryor links. In distributed settings, control/instructions may occur fromboth local and remote computer storage media including memory storagedevices.

Innovative software, circuitry and components herein may also includeand/or utilize one or more type of computer readable media. Computerreadable media can be any available media that is resident on,associable with, or can be accessed by such circuits and/or computingcomponents. By way of example, and not limitation, computer readablemedia may comprise computer storage media and communication media.Computer storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic tape, magnetic disk storage or other magnetic storagedevices, or any other medium which can be used to store the desiredinformation and can accessed by computing component. Communication mediamay comprise computer readable instructions, data structures, programmodules and/or other components. Further, communication media mayinclude wired media such as a wired network or direct-wired connection,however no media of any such type herein includes transitory media.Combinations of the any of the above are also included within the scopeof computer readable media.

In the present description, the terms component, module, device, etc.may refer to any type of logical or functional software elements,circuits, blocks and/or processes that may be implemented in a varietyof ways. For example, the functions of various circuits and/or blockscan be combined with one another into any other number of modules. Eachmodule may even be implemented as a software program stored on atangible memory (e.g., random access memory, read only memory, CD-ROMmemory, hard disk drive, etc.) to be read by a central processing unitto implement the functions of the innovations herein. Or, the modulescan comprise programming instructions transmitted to a general purposecomputer or to processing/graphics hardware via a transmission carrierwave. Also, the modules can be implemented as hardware logic circuitryimplementing the functions encompassed by the innovations herein.Finally, the modules can be implemented using special purposeinstructions (SIMD instructions), field programmable logic arrays or anymix thereof which provides the desired level performance and cost.

As disclosed herein, features consistent with the present inventions maybe implemented via computer-hardware, software and/or firmware. Forexample, the systems and methods disclosed herein may be embodied invarious forms including, for example, a data processor, such as acomputer that also includes a database, digital electronic circuitry,firmware, software, or in combinations of them. Further, while some ofthe disclosed implementations describe specific hardware components,systems and methods consistent with the innovations herein may beimplemented with any combination of hardware, software and/or firmware.Moreover, the above-noted features and other aspects and principles ofthe innovations herein may be implemented in various environments. Suchenvironments and related applications may be specially constructed forperforming the various routines, processes and/or operations accordingto the invention or they may include a general-purpose computer orcomputing platform selectively activated or reconfigured by code toprovide the necessary functionality. The processes disclosed herein arenot inherently related to any particular computer, network,architecture, environment, or other apparatus, and may be implemented bya suitable combination of hardware, software, and/or firmware. Forexample, various general-purpose machines may be used with programswritten in accordance with teachings of the invention, or it may be moreconvenient to construct a specialized apparatus or system to perform therequired methods and techniques.

Aspects of the method and system described herein, such as the logic,may also be implemented as functionality programmed into any of avariety of circuitry, including programmable logic devices (“PLDs”),such as field programmable gate arrays (“FPGAs”), programmable arraylogic (“PAL”) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits. Some other possibilities for implementing aspectsinclude: memory devices, microcontrollers with memory (such as EEPROM),embedded microprocessors, firmware, software, etc. Furthermore, aspectsmay be embodied in microprocessors having software-based circuitemulation, discrete logic (sequential and combinatorial), customdevices, fuzzy (neural) logic, quantum devices, and hybrids of any ofthe above device types. The underlying device technologies may beprovided in a variety of component types, e.g., metal-oxidesemiconductor field-effect transistor (“MOSFET”) technologies likecomplementary metal-oxide semiconductor (“CMOS”), bipolar technologieslike emitter-coupled logic (“ECL”), polymer technologies (e.g.,silicon-conjugated polymer and metal-conjugated polymer-metalstructures), mixed analog and digital, and so on.

It should also be noted that the various logic and/or functionsdisclosed herein may be enabled using any number of combinations ofhardware, firmware, and/or as data and/or instructions embodied invarious machine-readable or computer-readable media, in terms of theirbehavioral, register transfer, logic component, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) though again does not include transitorymedia. Unless the context clearly requires otherwise, throughout thedescription, the words “comprise,” “comprising,” and the like are to beconstrued in an inclusive sense as opposed to an exclusive or exhaustivesense; that is to say, in a sense of “including, but not limited to.”Words using the singular or plural number also include the plural orsingular number respectively. Additionally, the words “herein,”“hereunder,” “above,” “below,” and words of similar import refer to thisapplication as a whole and not to any particular portions of thisapplication. When the word “or” is used in reference to a list of two ormore items, that word covers all of the following interpretations of theword: any of the items in the list, all of the items in the list and anycombination of the items in the list.

Although certain presently preferred implementations of the inventionhave been specifically described herein, it will be apparent to thoseskilled in the art to which the invention pertains that variations andmodifications of the various implementations shown and described hereinmay be made without departing from the spirit and scope of theinvention. Accordingly, it is intended that the invention be limitedonly to the extent required by the applicable rules of law.

APPENDIX A ProductTypes SELECT ‘ProductTypes’ AS ACTION; DROP TABLE IFEXISTS ProductTypes; CREATE  TABLE IF NOT EXISTS ProductTypes(   productTypeId SMALLINT NOT NULL auto_increment,    productTypeNamevarchar(75),    uiGroup    varchar(20),    physical   boolean not nulldefault 0, -- physical real world item or in person event(if false isdigital item or event than can be transfered electronically)   experience   boolean not null default 0,  -- experience that happensin real time (physical or digital)    personalized   boolean not nulldefault 0, -- this item can be personalized, so need to ask user forpersonalization info when buying    usePresetEventTime  boolean not nulldefault 0, -- if true, use products.eventTime    produceByScheduleTime boolean not null default 0,  -- if true, useorderItemInfos.scheduleTime as the time the item needs to be produced by         -- as long as the item is produced before this time, all iswell    negotiateScheduleTime  boolean not null default 0,  -- if true,use orderItemInfos.scheduleTime to store the result of the schedulingprocess    allowVendorEntry boolean not null default 0,   --celebrity/vendors can enter products of this type    negotiableLocation  boolean not null default 0,   -- if false means fixed location   bestContactInfoNeeded   boolean not null default 0, - - if true,means ask for Best Phone number, best email to reach you AFTER CHECKOUT   occasionBeforeCheckoutNeeded   boolean not null default 0, - - iftrue, ask for occassion before checkout    occasionAfterCheckoutNeeded  boolean not null default 0, - - if true, ask for occasion aftercheckout    facebookIdNeeded  boolean not null default 0,   -- if true,will ask for facebook ID of the user or obtionally from the users listof friends    twitterHandleNeeded   boolean not null default 0, -- iftrue, will ask for the Twitter handle from the user    nameNeeded  boolean not null default 0,  - - ask for the users name   commentBeforeCheckoutNeeded  boolean not null default 0,  -- Must addcomments before checkout    commentAfterCheckoutNeeded   boolean notnull default 0,  -- Must add comments after checkout   eventTypeAfterCheckoutNeeded  boolean not null default 0,  -- ask forevent type after checkout    infoBeforeCheckoutNeeded  boolean not nulldefault 0, -- ask from info before checkout    nameAfterCheckoutNeeded    boolean not null default 0, - - ask for the users name aftercheckout    recipientEmailNeeded     boolean not null default 0,  -- askor recipient Email before checkout    primary key(productTypeId),   index(uiGroup) ) ENGINE = InnoDB;

APPENDIX B Flags in productTypes table replace into producttypes values(1, ‘Product Physical’,  “G2”,    1,0,0,0,0, 0,1,0,0,0,0, 0,0,0,0,0,0,0); replace into producttypes values (2, ‘Facebook Post’,  “G1”,   0,0,1,0,1, 0,1,0,0,0,0, 0,0,0,0,0, 0,0); replace into producttypesvalues (3, ‘Twitter Follow’,  “G1”,    0,0,1,0,1, 0,1,0,0,0,0,0,0,0,0,0, 0,0); replace into producttypes values (4, ‘Twitter ShoutOut’,  “G1”,    0,0,1,0,1, 0,1,0,0,0,0, 0,0,0,0,0, 0,0); replace intoproducttypes values (5, ‘Chat Video’,  “G1”,    0,1,1,0,0, 1,1,0,0,0,0,0,0,0,0,0, 0,0); replace into producttypes values (6, ‘Chat PhoneCall’,  “G1”,    0,1,1,0,0, 1,1,0,0,0,0, 0,0,0,0,0, 0,0); replace intoproducttypes values (7, ‘Event Physical’,  “G1”,   1,1,0,1,0, 0,0,0,1,0,0, 0,0,0,0,0, 0,0);        -- this is acelebrity happening that has a predefined date, time, and locationreplace into producttypes values (8, ‘Subscription’,  “G1”,   0,0,1,1,0, 0,0,0,0,0,0, 0,0,0,0,0, 0,0); replace into producttypesvalues (9, ‘Badge’,  “G1”,      0,0,1,0,1, 0,0,0,0,0,0, 0,0,0,0,0, 0,0);replace into producttypes values (10, ‘Event Pre-announce List’, “G1”,       0,0,0,1,0, 0,0,0,0,0,0, 0,0,0,0,0, 0,0); replace intoproducttypes values (11, ‘Message Video’,  “G1”,     0,0,1,0,1, 0,1,0,0,0,0, 0,0,0,0,0, 0,0); replace into producttypesvalues (12, ‘Meeting Scheduleable Digital’, “G1”,   0,1,1,0,0, 1,0,0,1,1,0, 0,0,0,0,0, 0,0);       -- this is a digitalhappening where the date, time and location is negotiable and can bechanged replace into producttypes values (13, ‘Meeting ScheduleablePhysical’,“G1”,         1,1,1,0,0, 1,0,0,1,1,0, 0,0,0,0,0, 0,0);      -- this is a digital happening where the date, time is negotiableand can be changed, the location is fixed replace into producttypesvalues (14, ‘Event Digital’,  “G1”,    0,1,0,1,0, 0,0,0,1,0,0,0,0,0,0,0, 0,0);    -- this is a celebrity happening that has apredefined date, time, and location replace into producttypes values(15, ‘Gift Certificate Digital’, “G1”,     0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0, 0,0); replace into producttypes values (16, ‘Gift CertificatePhysical’, “G1”,      1,0,0,0,0, 0,0,0,0,0,0, 0,0,0,0,0, 0,0); replaceinto producttypes values (17, ‘Meeting Scheduleable Physical Locationnegotiable’,“G1”,   1,1,1,0,0, 1,0,1,1,1,0, 0,0,0,0,0, 0,0);       -- 1this is a digital happening where the date, time, and LOCATION isnegotiable and can be changed replace into producttypes values (18,‘Product Physical Personalized’,“G2”,           1,0,1,0,0, 0,1,0,0,0,0, 0,0,0,0,0, 0,0);

The invention claimed is:
 1. A method of processing data comprising:processing, via a back end module of a computer system in communicationwith at least one other processor of the computer system, product dataand database entries from a first database associated with one or moreexperiences, one or more physical products, and one or more digitalproducts, wherein the database entries denote classification of theexperiences, the physical products, and the digital products usingspecified product type identifiers configured to be automaticallyprocessed and managed by the computer system, the product typeidentifiers including three or more of a physical product, a socialmedia product, an event, a physical meeting, and a digital meeting;wherein the classification of the product types includessub-classification utilizing various Boolean flags, including a productflag, an experience flag, a negotiate schedule time flag, a negotiablelocation flag, a vendor fulfill flag, and a gift flag; receiving, viathe backend module, data associated with a checkout of a purchasedproduct from a user; processing the purchased product via different userinterface screens as a function of the physical flag; determining, viathe backend module's processing of the gift flag, whether the purchasedproduct has been purchased as a gift; performing processing of aplurality of routines, the routines comprising: a first routine,executed when the purchased product has been purchased as a gift, forsending, via the backend module, a gift ticket to a recipient; a secondroutine for processing, via the backend module, a charge associated withthe purchased product; a third routine, executed when the purchasedproduct has not been purchased as a gift, for sending, with the backendmodule, a ticket to the user; a fourth routine, executed as a functionof the product type identifier being the physical event, the physicalmeeting or the digital meeting, for sending, via the backend module,information associated with the product to the vendor; a schedulingroutine for scheduling, via the backend module, a time, logistics andplace at which an activity associated with the purchased product willtake place, wherein the scheduling routine comprises: processinginformation regarding negotiation of schedule logistics based on thenegotiate schedule time flag and the negotiate location flag;determining, via the backend module, a scheduled time and a scheduledplace associated with the purchased product; and writing the schedulelogistic to a database; and sending, via the backend module, a reminderto the user and/or the recipient at a time before the scheduled timeassociated with the purchased product.
 2. The method of claim 1, furthercomprising: receiving, with the backend module, information associatedwith the purchase; and when the purchased product has not been purchasedas a gift, processing, with the backend module, the charge associatedwith the purchased product after receiving the information associatedwith the purchase.
 3. The method of claim 2, wherein the informationassociated with the purchase comprises background check information forthe user and/or the time and place associated with the purchasedproduct.
 4. The method of claim 1, wherein determining the time and/orplace comprises: determining, with the backend module, whether anexperience is prescheduled; when the experience is prescheduled,setting, with the backend module, the time and/or place as aprescheduled time and/or place; and when the experience is notprescheduled, receiving, with the backend module, a negotiated timeand/or place from a user and setting, with the backend module, the timeand/or place as the negotiated time and/or place.
 5. The method of claim1, wherein sending the reminder comprises: determining, with the backendmodule, a remaining time until the time associated with the purchasedproduct; and waiting until the remaining time reaches a threshold valuebefore sending the reminder.
 6. The method of claim 1, wherein thepurchased product is associated with product data comprising one or moreof a plurality of product types, one or more of a plurality of producttype flags which describe one or more of the plurality of product types,and one or more of a plurality of product type flag field definitionswhich define a characteristic of one or more of the plurality of producttype flags.
 7. The method of claim 6, wherein determining the timeand/or place comprises: determining, with the backend module, whether anexperience is prescheduled; when the experience is prescheduled,setting, with the backend module, the time and/or place as aprescheduled time and/or place; and when the experience is notprescheduled, receiving, via the backend module, a negotiated timeand/or place from a user and setting, via the backend module, the timeand/or place as the negotiated time and/or place.
 8. A method ofprocessing data comprising: processing, via a back end module of acomputer system in communication with at least one other processor ofthe computer system, product data and database entries from a firstdatabase associated with one or more experiences, one or morepersonalized products, and one or more digital products, wherein thedatabase entries denote classification of the experiences, thepersonalized products, and the digital products using specified producttype identifiers configured to be automatically processed and managed bythe computer system, the product type identifiers including three ormore of a subscription, a social media product, a physical event, adigital event, a physical meeting, and a digital meeting; wherein theclassification of the product types includes sub-classificationutilizing various Boolean flags, including a physical flag, an eventflag, a negotiate schedule time flag, a negotiable location flag, and avendor fulfill flag; receiving, via the backend module, data associatedwith a checkout of a purchased product from a user; processing thepurchased product via different user interface screens as a function ofthe Boolean flags; determining, via the backend module's processing ofthe physical flag, whether the purchased product is a physical or adigital product; performing processing of a plurality of routines, theroutines comprising: a first routine, executed via the backend module asa function of the product type identifier being the subscription, forperforming processing regarding providing exclusive content of thevendor to the user; a second routine for processing, via the backendmodule, a charge associated with the purchased product; a third routinefor sending, via the backend module, a confirmation ticket to the user;a fourth routine, executed as a function of the product type identifierbeing the physical event, the physical meeting or the digital meeting,for sending, via the backend module, information associated with theproduct to the vendor; a scheduling routine for scheduling, via thebackend module, a time, logistics and place at which an activityassociated with the purchased product will take place, wherein thescheduling routine comprises: processing information regardingnegotiation of schedule logistics based on the negotiate schedule timeflag and the negotiate location flag; determining, via the backendmodule, a scheduled time and/or a scheduled place associated with thepurchased product; and writing the schedule logistic to a database; andsending, via the backend module, a reminder to the user and/or therecipient at a time before the scheduled time associated with thepurchased product.
 9. The method of claim 8, further comprising:receiving, via the backend module, information associated with thepurchase; and when the purchased product has not been purchased as agift, processing, via the backend module, the charge associated with thepurchased product after receiving the information associated with thepurchase.
 10. The method of claim 9, wherein the information associatedwith the purchase comprises background check information for the userand/or the time and place associated with the purchased product.
 11. Themethod of claim 8, wherein determining the time and/or place comprises:determining, via the backend module, whether an experience isprescheduled; when the experience is prescheduled, setting, via thebackend module, the time and/or place as a prescheduled time and/orplace; and when the experience is not prescheduled, receiving, via thebackend module, a negotiated time and/or place from a user and setting,via the backend module, the time and/or place as the negotiated timeand/or place.
 12. The method of claim 8, wherein sending the remindercomprises: determining, via the backend module, a remaining time untilthe time associated with the purchased product; and waiting until theremaining time reaches a threshold value before sending the reminder.13. The method of claim 8, wherein the purchased product is associatedwith product data comprising one or more of a plurality of producttypes, one or more of a plurality of product type flags which describeone or more of the plurality of product types, and one or more of aplurality of product type flag field definitions which define acharacteristic of one or more of the plurality of product type flags.14. The method of claim 13, wherein determining the time and/or placecomprises: determining, via the backend module, whether an experience isprescheduled; when the experience is prescheduled, setting, via thebackend module, the time and/or place as a prescheduled time and/orplace; and when the experience is not prescheduled, receiving, via thebackend module, a negotiated time and/or place from a user and setting,via the backend module, the time and/or place as the negotiated timeand/or place.
 15. A method of processing data comprising: processing,via a back end module of a computer system in communication with atleast one other processor of the computer system, product data anddatabase entries from a first database associated with one or moreexperiences, one or more personalized products, and one or more digitalproducts, wherein the database entries denote classification of theexperiences, the personalized products, and the digital products usingspecified product type identifiers configured to be automaticallyprocessed and managed by the computer system, the product typeidentifiers including three or more of a personalized product, a socialmedia product, a physical event, a digital event, a physical meeting,and a digital meeting; wherein the classification of the product typesincludes sub-classification utilizing various Boolean flags, including aphysical flag, an event flag, a negotiate schedule time flag, anegotiable location flag, and an ispersonalized flag; receiving, via thebackend module, data associated with a checkout of a purchased productfrom a user; processing the purchased product via different userinterface screens as a function of one or more of the Boolean flags;determining, via the backend module's processing of the physical flag,whether the purchased product is a physical or a digital product;performing processing of a plurality of routines, the routinescomprising: a first routine, executed as a function of the event flag,for processing the purchased product via the backend module through oneor more event stages and/or GUIs; a second routine for processing, viathe backend module, a charge associated with the purchased product; athird routine for sending, via the backend module, a confirmation ticketto the user; a fourth routine, executed as a function of the producttype identifier being the physical event, the physical meeting or thedigital meeting, for sending, via the backend module, informationassociated with the product to the vendor; a scheduling routine forscheduling, via the backend module, a time, logistics and place at whichan activity associated with the purchased product will take place,wherein the scheduling routine comprises: processing informationregarding negotiation of schedule logistics based on the negotiateschedule time flag and the negotiate location flag; determining, via thebackend module, a scheduled time and/or a scheduled place associatedwith the purchased product; and writing the schedule logistic to adatabase; and sending, via the backend module, a reminder to the userand/or the recipient at a time before the scheduled time associated withthe purchased product.
 16. The method of claim 15, further comprising:receiving, via the backend module, information associated with thepurchase; and when the purchased product has not been purchased as agift, processing, via the backend module, the charge associated with thepurchased product after receiving the information associated with thepurchase.
 17. The method of claim 16, wherein the information associatedwith the purchase comprises background check information for the userand/or the time and place associated with the purchased product.
 18. Themethod of claim 15, wherein determining the time and/or place comprises:determining, via the backend module, whether an experience isprescheduled; when the experience is prescheduled, setting, via thebackend module, the time and/or place as a prescheduled time and/orplace; and when the experience is not prescheduled, receiving, via thebackend module, a negotiated time and/or place from a user and setting,via the backend module, the time and/or place as the negotiated timeand/or place.
 19. The method of claim 15, wherein sending the remindercomprises: determining, via the backend module, a remaining time untilthe time associated with the purchased product; and waiting until theremaining time reaches a threshold value before sending the reminder.20. The method of claim 15, wherein the purchased product is associatedwith product data comprising one or more of a plurality of producttypes, one or more of a plurality of product type flags which describeone or more of the plurality of product types, and one or more of aplurality of product type flag field definitions which define acharacteristic of one or more of the plurality of product type flags.21. The method of claim 20, wherein determining the time and/or placecomprises: determining, via the backend module, whether an experience isprescheduled; when the experience is prescheduled, setting, via thebackend module, the time and/or place as a prescheduled time and/orplace; and when the experience is not prescheduled, receiving, via thebackend module, a negotiated time and/or place from a user and setting,via the backend module, the time and/or place as the negotiated timeand/or place.
 22. A method of processing data comprising: processing,via a back end module of a computer system in communication with atleast one other processor of the computer system, product data anddatabase entries from a first database associated with one or moreexperiences, one or more personalized products, and one or more digitalproducts, wherein the database entries denote classification of theexperiences, the personalized products, and the digital products usingspecified product type identifiers configured to be automaticallyprocessed and managed by the computer system, the product typeidentifiers including three or more of a personalized product, a socialmedia product, a physical event, a digital event, a physical meeting,and a digital meeting; wherein the classification of the product typesincludes sub-classification utilizing various Boolean flags, including aphysical flag, an ispersonalized flag, a negotiate schedule time flag, anegotiable location flag, and a vendor fulfill flag; receiving, via thebackend module, data associated with a checkout of a purchased productfrom a user; processing the purchased product via different userinterface screens as a function of the Boolean flags; determining, viathe backend module's processing of the physical flag, whether thepurchased product is a physical or a digital product; performingprocessing of a plurality of routines, the routines comprising: a firstroutine, executed via the backend module as a function of the vendorfulfill flag, for performing processing regarding provision ofinformation to a fulfillment section of a vendor administration GUI; asecond routine for processing, via the backend module, a chargeassociated with the purchased product; a third routine for sending, viathe backend module, a confirmation ticket to the user; a fourth routine,executed as a function of the product type identifier being the physicalevent, the physical meeting or the digital meeting, for sending, via thebackend module, information associated with the product to the vendor; ascheduling routine for scheduling, via the backend module, a time,logistics and place at which an activity associated with the purchasedproduct will take place, wherein the scheduling routine comprises:processing information regarding negotiation of schedule logistics basedon the negotiate schedule time flag and the negotiate location flag;determining, via the backend module, a scheduled time and/or a scheduledplace associated with the purchased product; and writing the schedulelogistic to a database; and sending, via the backend module, a reminderto the user and/or the recipient at a time before the scheduled timeassociated with the purchased product.
 23. The method of claim 22,further comprising: receiving, via the backend module, informationassociated with the purchase; and when the purchased product has notbeen purchased as a gift, processing, via the backend module, the chargeassociated with the purchased product after receiving the informationassociated with the purchase.
 24. The method of claim 23, wherein theinformation associated with the purchase comprises background checkinformation for the user and/or the time and place associated with thepurchased product.
 25. The method of claim 22, wherein determining thetime and/or place comprises: determining, via the backend module,whether an experience is prescheduled; when the experience isprescheduled, setting, via the backend module, the time and/or place asa prescheduled time and/or place; and when the experience is notprescheduled, receiving, via the backend module, a negotiated timeand/or place from a user and setting, via the backend module, the timeand/or place as the negotiated time and/or place.
 26. The method ofclaim 22, wherein sending the reminder comprises: determining, via thebackend module, a remaining time until the time associated with thepurchased product; and waiting until the remaining time reaches athreshold value before sending the reminder.
 27. The method of claim 22,wherein the purchased product is associated with product data comprisingone or more of a plurality of product types, one or more of a pluralityof product type flags which describe one or more of the plurality ofproduct types, and one or more of a plurality of product type flag fielddefinitions which define a characteristic of one or more of theplurality of product type flags.
 28. The method of claim 27, whereindetermining the time and/or place comprises: determining, via thebackend module, whether an experience is prescheduled; when theexperience is prescheduled, setting, via the backend module, the timeand/or place as a prescheduled time and/or place; and when theexperience is not prescheduled, receiving, via the backend module, anegotiated time and/or place from a user and setting, via the backendmodule, the time and/or place as the negotiated time and/or place.